chore: migrate to pnpm 11 + add minimumReleaseAge#202
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pnpm 9 (used by Vercel by default) was enforcing engines.node on transitive deps. The packages/web nuxt devDep chain requires Node 22+, but the Vercel sveltekit project runs Node 20, blocking install of the entire workspace even though sveltekit doesn't use nuxt. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was a no-op; Node version bumped on the Vercel project instead. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The external https://va.vercel-scripts.com/v1/script.debug.js changed its pageview log prefix from `[pageview]` to `[view]`, breaking the dev e2e tests on main since around March 2026. Update the two affected specs to match the current upstream format. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
dferber90
approved these changes
May 21, 2026
feugy
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🖖 What's in there?
Upgrade pnpm from v8.6.5 to v11.1.3 to leverage performance improvements and stricter dependency resolution. This is a major version jump that requires adjustments to lockfile format, allowlist configuration for packages with lifecycle scripts, and explicit pinning of React peer dependencies in web package to maintain version consistency across tests.
🔬 Notes to reviewers
pnpm v10+ enforces stricter lifecycle script policies by default, blocking dependency build scripts unless explicitly allowed. The
pnpm-workspace.yamlnow includes anallowBuildsallowlist for 6 packages that require build-time scripts:@parcel/watcher,@swc/core,esbuild,lefthook,sharp, andunrs-resolver.pnpm v11's stricter peer dependency resolution split React and ReactDOM into separate major versions (react@18 + react-dom@19) when pulled transitively. Both are now explicitly pinned to
^18.3.1inpackages/web/package.jsondevDependencies to keep them in lockstep and prevent test failures.The lockfile format has been upgraded from v6 to v9. CI integration requires no changes—the pipeline uses corepack and respects the
packageManagerfield inpackage.json.